resolve RIP in some x86 fp semantics - #1637

Net effect of the reverted conflict-tolerance experiment: the driver and CFG keep the surviving conflict-tolerant reads.

opam builds with 'dune build -p NAME', which is shorthand for
--release; the -O3 lived only in the dev profile, so every opam-built
bap was compiled with -g and no -O3.

RelocationRef has no getAddend on this LLVM; the ELF-specific ref
does, and its addend is an Expected.  The table row emitted is
unchanged.

The ogre doc parse rejects every entry whose table the scheme does
not declare; the addend rows made the whole doc unparseable.

The scalar min/max replaced all 128 bits with the selected operand; the
destination's upper quadword is preserved.

The double-width result temporary made RAX and RDX extracts of a
concatenation; each register now takes its half directly.

Each x87 instruction lifts to an x87_* intrinsic over its memory
operands and flags; FPU_CONTROL is declared as a target register.

A word wider than the memory's native stores was written with each
chunk shifted one chunk too far and in the opposite byte order.